Methods and devices for displaying data mark information

ABSTRACT

A method includes displaying at least a first portion of a chart at a first magnification, the first portion containing a plurality of data marks. The method also includes detecting a first input at a location that corresponds to the first portion of the chart and, in response, zooming in to display a second portion of the chart at a second magnification, the second portion including a first data mark in the plurality of data marks. The method further includes detecting a second touch input at a location that corresponds to the second portion of the chart, and, in response: if one or more predefined data-mark-information-display criteria are not met, zooming in to display a third portion of the chart at a third magnification, the third portion including the first data mark; and, if the one or more predefined data-mark-information-display criteria are met, displaying information about the first data mark.

RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser. No. 62/047,429, filed Sep. 8, 2014, entitled “Methods and Devices for Manipulating Graphical Views of Data,” which is incorporated by reference herein in its entirety.

This application is related to U.S. patent application Ser. No. 14/603,302, filed Jan. 22, 2015, entitled “Methods and Devices for Adjusting Chart Filters,” U.S. patent application Ser. No. 14/603,312, filed Jan. 22, 2015, entitled “Methods and Devices for Adjusting Chart Magnification Asymmetrically,” and U.S. patent application Ser. No. 14/603,330, filed Jan. 22, 2015, entitled “Methods and Devices for Adjusting Chart Magnification,” each of which is incorporated by reference herein in its entirety.

TECHNICAL FIELD

This invention relates generally to devices and methods for displaying graphical views of data. The invention relates specifically to devices and methods for manipulating user interfaces displaying graphical views of data.

BACKGROUND

Data sets with hundreds of variables or more arise today in many contexts, including, for example: gene expression data for uncovering the link between the genome and the various proteins for which it codes; demographic and consumer profiling data for capturing underlying sociological and economic trends; sales and marketing data for huge numbers of products in vast and ever-changing marketplaces; and environmental measurements for understanding phenomena such as pollution, meteorological changes, and resource impact issues.

Data visualization is a powerful tool for exploring large data sets, both by itself and coupled with data mining algorithms. Graphical views provide user-friendly ways to visualize and interpret data. However, the task of effectively visualizing large databases imposes significant demands on the human-computer interface to the visualization system.

In addition, as computing and networking speeds increase, data visualization that was traditionally performed on desktop computers can also be performed on portable electronic devices, such as smart phones, tablets, and laptop computers. These portable devices typically use touch-sensitive surfaces (e.g., touch screens and/or trackpads) as input devices. These portable devices typically have significantly smaller displays than desktop computers. Thus, additional challenges arise in using touch-sensitive surfaces to manipulate graphical views of data in a user-friendly manner on portable devices.

Consequently, there is a need for faster, more efficient methods and interfaces for manipulating graphical views of data. Such methods and interfaces may complement or replace conventional methods for visualizing data. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated devices, such methods and interfaces conserve power and increase the time between battery charges.

SUMMARY

The above deficiencies and other problems associated with visualizing data are reduced or eliminated by the disclosed methods, devices, and storage mediums. Various implementations of methods, devices, and storage mediums within the scope of the appended claims each have several aspects, no single one of which is solely responsible for the attributes described herein. Without limiting the scope of the appended claims, after considering this disclosure, one will understand how the aspects of various implementations are used to visualize data.

In one aspect, some embodiments include methods for visualizing data.

In some embodiments, a method is performed at an electronic device with a touch-sensitive surface and a display. The method includes displaying at least a first portion of a chart on the display at a first magnification, the first portion of the chart containing a plurality of data marks. The method also includes detecting a first touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the first portion of the chart and, in response to detecting the first touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the first portion of the chart, zooming in to display a second portion of the chart at a second magnification, the second portion of the chart including a first data mark in the plurality of data marks. The method further includes, while displaying the second portion of the chart at the second magnification, detecting a second touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the second portion of the chart. The method further includes, in response to detecting the second touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart: in accordance with a determination that one or more predefined data-mark-information-display criteria are not met, zooming in to display a third portion of the chart at a third magnification, the third portion of the chart including the first data mark in the plurality of data marks; and, in accordance with a determination that the one or more predefined data-mark-information-display criteria are met, displaying information about the first data mark.

In some embodiments, the second touch input is a same type of touch input as the first touch input.

In some embodiments, the information about the first data mark comprises a data record that corresponds to the first data mark.

In some embodiments, the data-mark-information-display criteria include the second magnification being a predefined magnification.

In some embodiments, the data-mark-information-display criteria include the first data mark in the plurality of data marks being the only data mark displayed at the second magnification after the first touch input.

In some embodiments, the data-mark-information-display criteria include the first data mark reaching a predefined magnification during the second touch input.

In some embodiments, the data-mark-information-display criteria include the device zooming in to display only the first data mark in the plurality of data marks during the second touch input.

In some embodiments, the method includes, in accordance with the determination that one or more predefined data-mark-information-display criteria are met, ceasing to display the first data mark.

In another aspect, some embodiments include electronic devices for visualizing data. In some embodiments, an electronic device for visualizing data includes a display, a touch-sensitive surface, one or more processors, memory, and one or more programs stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for displaying at least a first portion of a chart on the display at a first magnification, the first portion of the chart containing a plurality of data marks. The one or more programs also include instructions for detecting a first touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the first portion of the chart and, in response to detecting the first touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the first portion of the chart, zooming in to display a second portion of the chart at a second magnification, the second portion of the chart including a first data mark in the plurality of data marks. The one or more programs further include instructions for, while displaying the second portion of the chart at the second magnification, detecting a second touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the second portion of the chart. The one or more programs further include instructions for, in response to detecting the second touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart: in accordance with a determination that one or more predefined data-mark-information-display criteria are not met, zooming in to display a third portion of the chart at a third magnification, the third portion of the chart including the first data mark in the plurality of data marks; and, in accordance with a determination that the one or more predefined data-mark-information-display criteria are met, displaying information about the first data mark.

In some embodiments, an electronic device for visualizing data includes a display, a touch-sensitive surface, one or more processors, memory, and one or more programs stored in the memory and configured to be executed by the one or more processors. The one or more programs include instructions for performing any of the methods described herein.

In yet another aspect, some embodiments include a non-transitory computer readable storage medium, storing one or more programs for execution by one or more processors of an electronic device with a display and a touch-sensitive surface, the one or more programs including instructions for performing any of the methods described herein.

In yet another aspect, some embodiments include a graphical user interface on an electronic device with a display, a touch-sensitive surface, a memory, and one or more processors to execute one or more programs stored in the memory, the graphical user interface comprising user interfaces displayed in accordance with any of the methods described herein.

Thus, electronic devices with displays and touch-sensitive surfaces are provided with faster, more efficient methods and interfaces for data visualization, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace conventional methods for data visualization.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the present disclosure can be understood in greater detail, a more particular description may be had by reference to the features of various implementations, some of which are illustrated in the appended drawings. The appended drawings, however, merely illustrate the more pertinent features of the present disclosure and are therefore not to be considered limiting, for the description may admit to other effective features.

FIG. 1 illustrates a portable multifunction device having a touch screen, in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch-sensitive surface that is separate from the display, in accordance with some embodiments.

FIG. 3A is a block diagram illustrating a portable multifunction device having a touch screen, in accordance with some embodiments.

FIG. 3B is a block diagram illustrating a portable multifunction device having a touch-sensitive surface, in accordance with some embodiments.

FIGS. 4A-4B illustrate user interfaces for initiating data visualization, in accordance with some embodiments.

FIGS. 5A-5G illustrate user interfaces for adjusting chart filters, in accordance with some embodiments.

FIGS. 6A-6L illustrate user interfaces for changing chart categories, in accordance with some embodiments.

FIGS. 7A-7D illustrate user interfaces for adjusting chart filters, in accordance with some embodiments.

FIGS. 8A-8D illustrate user interfaces for adjusting chart filters, in accordance with some embodiments.

FIGS. 9A-9B illustrate user interfaces for changing chart views, in accordance with some embodiments.

FIGS. 10A-10B illustrate user interfaces for adjusting a chart view, in accordance with some embodiments.

FIGS. 11A-11J illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments.

FIGS. 12A-12D illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments.

FIGS. 13A-13D illustrate user interfaces for selecting chart areas, in accordance with some embodiments.

FIGS. 14A-14D illustrate user interfaces for exporting data visualizations, in accordance with some embodiments.

FIGS. 15A-15C illustrate user interfaces for adjusting a chart view, in accordance with some embodiments.

FIGS. 16A-16D illustrate user interfaces for changing chart categories, in accordance with some embodiments.

FIGS. 17A-17B illustrate user interfaces for selecting chart areas, in accordance with some embodiments.

FIGS. 18A-18E illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments.

FIGS. 19A-19D illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments.

FIGS. 19E-19L illustrate user interfaces for displaying information about a data mark, in accordance with some embodiments.

FIGS. 20A-20B provide a flow diagram illustrating a method of data visualization in accordance with some embodiments.

FIGS. 21A-21F illustrate scrolling filters in accordance with some embodiments.

In accordance with common practice, the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system or device. Finally, like reference numerals may be used to denote like features throughout the specification and figures.

DESCRIPTION OF EMBODIMENTS

As portable electronic devices become more compact, and the number of functions performed by applications on any given device increase, it has become a significant challenge to design user interfaces that allow users to interact with the applications easily. This challenge is particularly significant for portable devices with smaller screens and/or limited input devices. In addition, data visualization applications need to provide user-friendly ways to explore data in order to enable a user to extract significant meaning from a particular data set. Some application designers have resorted to using complex menu systems to enable a user to perform desired functions. These conventional user interfaces often result in complicated key sequences and/or menu hierarchies that must be memorized by the user, and/or that are otherwise cumbersome and/or not intuitive to use.

The methods, devices, and GUIs described herein make manipulation of data sets and data visualizations more efficient and intuitive for a user. A number of different intuitive user interfaces for data visualizations are described below. For example, applying a filter to a data set can be accomplished by a simple touch input on a given portion of a displayed chart rather than via a nested menu system. Additionally, switching between chart categories can be accomplished by a simple touch input on a displayed chart label.

FIGS. 20A-20B provide a flow diagram illustrating a method of displaying information about a data mark. FIGS. 19E-19L illustrate user interfaces for displaying information about a data mark. The user interfaces in FIGS. 19E-19L are used to illustrate the processes in FIGS. 20A-20B.

Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.

Attention is now directed toward embodiments of portable devices with touch-sensitive displays. Embodiments of electronic devices and user interfaces for such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, a microphone, and/or a joystick.

FIG. 1 illustrates portable multifunction device 100 having touch screen 102, in accordance with some embodiments. In some embodiments, device 100 is a mobile phone, a laptop computer, a personal digital assistant (PDA), or a tablet computer. The touch screen 102 is also sometimes called a touch-sensitive display and/or a touch-sensitive display system. Touch screen 102 optionally displays one or more graphics within a user interface (UI). In some embodiments, a user is enabled to select one or more of the graphics by making a touch input (e.g., touch input 108) on the graphics. In some instances, the touch input is a contact on the touch screen. In some instances, the touch input is a gesture that includes a contact and movement of the contact on the touch screen. In some instances, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. For example, a touch input on the graphics is optionally made with one or more fingers 110 (not drawn to scale in the figure) or one or more styluses 112 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over a visual mark optionally does not select the visual mark when the gesture corresponding to selection is a tap. Device 100 optionally also includes one or more physical buttons and/or other input/output devices, such as a microphone for verbal inputs.

FIG. 2 illustrates multifunction device 200 in accordance with some embodiments. Device 200 need not be portable. In some embodiments, device 200 is a laptop computer, a desktop computer, a tablet computer, or an educational device. Device 200 includes screen 202 and touch-sensitive surface 204. Screen 202 optionally displays one or more graphics within a UI. In some embodiments, a user is enabled to select one or more of the graphics by making a touch input (e.g., touch input 210) on touch-sensitive surface 204 such that a corresponding cursor (e.g., cursor 212) on screen 202 selects the one or more graphics. For example, when an input is detected on touch-sensitive surface 204 while cursor 212 is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input.

FIG. 3A is a block diagram illustrating portable multifunction device 100, in accordance with some embodiments. It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 3A are implemented in hardware, software, firmware, or a combination of hardware, software, and/or firmware, including one or more signal processing and/or application specific integrated circuits.

Device 100 includes one or more processing units (CPU's) 302, input/output (I/O) subsystem 306, memory 308 (which optionally includes one or more computer readable storage mediums), and network communications interface 310. These components optionally communicate over one or more communication buses or signal lines 304. Communication buses 304 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.

Memory 308 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 308 optionally includes one or more storage devices remotely located from processor(s) 302. Memory 308, or alternately the non-volatile memory device(s) within memory 308, comprises a non-transitory computer readable storage medium.

In some embodiments, the software components stored in memory 308 include operating system 318, communication module 320, input/output (I/O) module 322, and applications 328. In some embodiments, one or more of the various modules comprises a set of instructions in memory 308. In some embodiments, memory 308 stores one or more data sets in one or more database(s) 332.

Operating system 318 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware, software, and/or firmware components.

Communication module 320 facilitates communication with other devices over one or more external ports and also includes various software components for handling data received from other devices.

I/O module 322 includes touch input sub-module 324 and graphics sub-module 326. Touch input sub-module 324 optionally detects touch inputs with touch screen 102 and other touch sensitive devices (e.g., a touchpad or physical click wheel). Touch input sub-module 324 includes various software components for performing various operations related to detection of a touch input, such as determining if contact has occurred (e.g., detecting a finger-down event), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Touch input sub-module 324 receives contact data from the touch-sensitive surface (e.g., touch screen 102). These operations are, optionally, applied to single touch inputs (e.g., one finger contacts) or to multiple simultaneous touch inputs (e.g., “multitouch”/multiple finger contacts). In some embodiments, touch input sub-module 324 detects contact on a touchpad.

Touch input sub-module 324 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns. Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an data mark). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.

Graphics sub-module 326 includes various known software components for rendering and displaying graphics on touch screen 102 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation data visualizations, icons (such as user-interface objects including soft keys), text, digital images, animations and the like. In some embodiments, graphics sub-module 326 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics sub-module 326 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to the display or touch screen.

Applications 328 optionally include data visualization module 330 for displaying graphical views of data and one or more other applications. Examples of other applications that are, optionally, stored in memory 308 include word processing applications, email applications, and presentation applications.

In conjunction with I/O interface 306, including touch screen 102, CPU(s) 302, and/or database(s) 332, data visualization module 330 includes executable instructions for displaying and manipulating various graphical views of data.

Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 308 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 308 optionally stores additional modules and data structures not described above.

FIG. 3B is a block diagram illustrating multifunction device 200, in accordance with some embodiments. It should be appreciated that device 200 is only one example of a multifunction device, and that device 200 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 3B are implemented in hardware, software, firmware, or a combination of hardware, software, and/or firmware, including one or more signal processing and/or application specific integrated circuits.

Device 200 typically includes one or more processing units/cores (CPUs) 352, one or more network or other communications interfaces 362, memory 350, I/O interface 356, and one or more communication buses 354 for interconnecting these components. Communication buses 354 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components.

I/O interface 306 comprises screen 202 (also sometimes called a display), touch-sensitive surface 204, and one or more sensor(s) 360 (e.g., optical, acceleration, proximity, and/or touch-sensitive sensors). I/O interface 356 optionally includes a keyboard and/or mouse (or other pointing device) 358. I/O interface 356 couples input/output peripherals on device 200, such as screen 202, touch-sensitive surface 204, other input devices 358, and one or more sensor(s) 360, to CPU(s) 352 and/or memory 350.

Screen 202 provides an output interface between the device and a user. Screen 202 displays visual output to the user. The visual output optionally includes graphics, text, icons, data marks, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output corresponds to user-interface objects. Screen 202 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments.

In addition to the touch screen, device 200 includes touch-sensitive surface 204 (e.g., a touchpad) for detecting touch inputs. Touch-sensitive surface 204 accepts input from the user via touch inputs. For example, touch input 210 in FIG. 2. Touch-sensitive surface 204 (along with any associated modules and/or sets of instructions in memory 350) detects touch inputs and converts the detected inputs into interaction with user-interface objects (e.g., one or more icons, data marks, or images) that are displayed on screen 202. In an exemplary embodiment, a point of contact between touch-sensitive surface 204 and the user corresponds to a finger of the user.

Memory 350 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 350 optionally includes one or more storage devices remotely located from CPU(s) 352. In some embodiments, the software components stored in memory 350 include operating system 364, communication module 366, input/output (I/O) module 368, and applications 374. In some embodiments, one or more of the various modules comprises a set of instructions in memory 350. In some embodiments, memory 350 stores one or more data sets in one or more database(s) 378. In some embodiments, I/O module 368 includes touch input sub-module 370 and graphics sub-module 372. In some embodiments, applications 374 include data visualization module 376.

In some embodiments, memory 350 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 308 of portable multifunction device 100 (FIG. 3A), or a subset thereof. Furthermore, memory 350 optionally stores additional programs, modules, and data structures not present in memory 308 of portable multifunction device 100. For example, memory 350 of device 200 optionally stores drawing, presentation, and word processing applications, while memory 308 of portable multifunction device 100 (FIG. 3A) optionally does not store these modules.

Device 200 also includes a power system for powering the various components. The power system optionally includes a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management, and distribution of power in portable devices.

Each of the above identified elements in FIG. 3B is, optionally, stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules are, optionally, combined or otherwise re-arranged in various embodiments. In some embodiments, memory 350 optionally stores a subset of the modules and data structures identified above. Furthermore, memory 350 optionally stores additional modules and data structures not described above.

Attention is now directed towards embodiments of user interfaces (“UI”) that are, optionally, implemented on portable multifunction device 100 or device 200. The following examples are shown utilizing a touch screen (e.g., touch screen 102 in FIG. 1). However, it should be understood that, in some embodiments, the inputs (e.g., finger contacts) are detected on a touch-sensitive surface on a device that is distinct from a display on the device. In addition, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.

FIGS. 4A-4B illustrate user interfaces for initiating data visualization, in accordance with some embodiments. FIG. 4A shows UI 402 including an email application. The email application contains an email including attached file 402. FIG. 4A also shows contact 410 over the icon corresponding to file 402. FIG. 4B shows UI 450 including a data visualization application. The data visualization application includes a graphical view of data from file 402. The graphical view includes chart 404 (e.g., a bar chart) with chart label 406, a plurality of categories, and a plurality of category labels 408. In some embodiments, file 402 has a file type associated with the data visualization application and, in response to detecting contact 410, the data visualization application is initialized and the data from file 402 is displayed in a graphical view.

FIGS. 5A-5G illustrate user interfaces for adjusting chart filters, in accordance with some embodiments. FIG. 5A shows UI 450 including category 502-1 and category label 408-1. FIG. 5A also shows contact 510 detected at position 510-a corresponding to the visual mark (e.g., a bar corresponding to category 502-1) for category 502-1. FIG. 5B shows UI 520 including contact 510 detected at position 510-b and the visual mark for category 502-1 moving in concert with movement of contact 510 via an animated transition. FIG. 5C shows UI 522 including contact 510 detected at position 510-c and the visual mark for category 502-1 continuing to move in concert with movement of contact 510 via an animated transition. FIG. 5C also shows indicium 504 indicating that category 502-1 (Catering) is being filtered out of the data as a result of the current action (e.g., the movement of contact 510). FIG. 5D shows UI 524 including indicium 504, contact 510 detected at position 510-d, and the visual mark for category 502-1 continuing to move in concert with movement of a contact 510 via an animated transition. FIG. 5E shows UI 526 including indicium 504 and the removal of the visual mark for category 502-1 from the chart.

FIG. 5F shows UI 528 including indicium 504, contact 510 detected at position 510-e, and the visual mark for category 502-1 continuing to move in concert with movement of a contact 510 via an animated transition. FIG. 5G shows UI 530 including indicium 506, contact 510 detected at position 510-f, and the visual mark for category 502-1 continuing to move in concert with movement of a contact 510 via an animated transition. In some embodiments, as shown in FIGS. 5A-5E, the first category and the first visual mark are removed from the chart via an animated transition in response to contact 510 moving to a pre-defined location. In some embodiments, as shown in FIGS. 5F-5G, the first category and the first visual mark are added back to the chart via an animated transition in response to contact 510 moving away from the pre-defined location.

FIGS. 6A-6L illustrate user interfaces for changing chart categories, in accordance with some embodiments. FIG. 6A shows UI 601 including a chart with chart label 602-1 (Menu Item) and categories 502 (including categories 502-1 through 502-13) with category labels 408. FIG. 6A also shows contact 610 detected at position 610-a corresponding to chart label 602-1. FIGS. 6B and 6C show contact 610 moving to position 610-b and 610-c respectively and the first chart with chart label 602-1 (Menu Item) being replaced by a second chart with chart label 602-2 (Menu Group) via an animated transition. FIGS. 6B and 6C also show chart categories 502 being replaced by categories 604 via an animated transition, and category labels 408 being replaced by category labels 606 via an animated transition.

FIG. 6D shows UI 607 including the second chart with chart label 602-2 (Menu Group) and categories 604 with category labels 606. FIG. 6D also shows contact 620 detected at position 620-a corresponding to chart label 602-2. FIGS. 6E and 6F show contact 620 moving to positions 620-b and 620-c respectively and the second chart with chart label 602-2 (Menu Group) being replaced by a third chart with chart label 602-3 (Day) via an animated transition. FIGS. 6E and 6F also show chart categories 604 being replaced by categories 612 via an animated transition, and category labels 606 being replaced by category labels 614 via an animated transition.

FIG. 6G shows UI 613 including the third chart with chart label 602-3 (Day) and categories 612 with category labels 614. FIG. 6G also shows contact 630 detected at a position corresponding to chart label 602-3 and selection menu 616 displayed. In some embodiments, contact 630 is detected and identified as a tap input and selection menu 616 is displayed in response. FIG. 6H shows UI 615 with selection menu 616 including selection categories 618. FIG. 6H also shows contact 640 detected at a position corresponding to selection category 618-2. FIG. 6I shows UI 617 including a fourth chart with chart label 602-4 (Hour) and categories 622 with category labels 624. In some embodiments, the chart shown in FIG. 6I replaces the chart shown in FIG. 6H in response to the detection of contact 640 at a position corresponding to selection category 618-2.

FIG. 6J shows UI 619 including the fourth chart with chart label 602-4 (Hour) and categories 622 with category labels 624. FIG. 6J also shows contact 650 detected at position 650-a corresponding to chart label 602-4. FIGS. 6K and 6L show contact 650 moving to positions 650-b and 650-c respectively and the fourth chart with chart label 602-4 (Hour) being replaced by the first chart with chart label 602-1 (Menu Item) via an animated transition. FIGS. 6K and 6L also show chart categories 622 being replaced by categories 502 via an animated transition, and category labels 624 being replaced by category labels 408 via an animated transition.

FIGS. 7A-7D illustrate user interfaces for adjusting chart filters, in accordance with some embodiments. FIG. 7A shows UI 701 including a chart with categories 612 (including category 612-4) and corresponding category labels 614. FIG. 7A also shows indicium 504 indicating that data corresponding to category 502-1 has been filtered out of the chart. FIG. 7A further shows contact 710 detected at position 710-a corresponding to indicium 504. FIGS. 7B and 7C show contact 710 moving to positions 710-b and 710-c respectively and the removal of indicium 504 along with the chart updating reflect inclusion of data that corresponds to category 502-1. FIGS. 7B and 7C also show categories 612 reordered to reflect inclusion of the data corresponding to category 502-1.

FIG. 7D shows UI 707 including indicium 504, contact 720 detected at a position corresponding to indicium 504, and categories 612. In some embodiments, as shown in FIGS. 7A-7C, the chart is updated to reflect inclusion of data that corresponds to category 502-1 in response to contact 710 moving from a pre-defined location or area on the UI. In some embodiments, as shown in FIG. 7D, the chart is updated to reflect exclusion of data that corresponds to category 502-1 in response to contact 720.

FIGS. 8A-8D illustrate user interfaces for adjusting chart filters, in accordance with some embodiments. FIG. 8A shows UI 801 including category 502-2 and category label 408-2. FIG. 8A also shows contact 810 detected at position 810-a corresponding to the visual mark for category 502-2 (e.g., a bar corresponding to category 502-2). FIGS. 8B and 8C show contact 810 moving to positions 810-b and 810-c respectively and the visual mark for category 502-2 moving in concert with movement of contact 810 via an animated transition. FIGS. 8B and 8C also show indicium 802 indicating that only the data corresponding to category 502-2 is being included as a result of the current action (e.g., the movement of contact 810). FIG. 8D shows UI 805 including indicium 802 and the removal of the visual mark for all categories except for category 502-1.

FIGS. 9A-9B illustrate user interfaces for changing chart views, in accordance with some embodiments. FIG. 9A shows UI 901 including indicium 802 and a bar chart with category 502-2. FIG. 9A also shows contact 910 detected at a position on UI 901 that corresponds to a line chart graphical view. FIG. 9B shows UI 903 including indicium 802 and a line chart. In some embodiments, the bar chart shown in FIG. 9A is replaced by the line chart shown in FIG. 9B in response to detection of contact 910 at a position on UI 901 that corresponds to a line chart graphical view.

FIGS. 10A-10B illustrate user interfaces for adjusting a chart view, in accordance with some embodiments. FIG. 10A shows UI 1001 including a chart. FIG. 10A also shows contact 1010 detected at position 1010-a on UI 1001. FIG. 10B shows contact 1010 at position 1010-b and movement of the chart in concert with movement of contact 1010.

FIGS. 11A-11J illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments. FIG. 11A shows UI 1101 including a chart at a first magnification (e.g., a first zoom level). FIG. 11A also shows contacts 1110 and 1120 detected at positions 1110-a and 1120-a respectively. FIG. 11B shows contacts 1110 and 1120 detected at positions 1110-b and 1120-b respectively and shows UI 1103 including the chart at a second magnification (e.g., zoomed in from the first zoom level). The relative positions of contacts 1110 and 1120 in FIG. 11B are further apart than the positions of contacts 1110 and 1120 in FIG. 11A and represent a de-pinch gesture on the touch screen. The second magnification of the chart shown in FIG. 11B includes the same vertical scale as the first magnification of the line shown in FIG. 11A. FIGS. 11C and 11D show an animated transition of the chart to a third magnification. The animated transition shown in FIGS. 11C and 11D includes an increase in the vertical scale of the chart. In some embodiments, the animated transition shown in FIGS. 11C and 11D is in response to ceasing to detect contacts 1110 and 1120 (e.g., detecting lift off of the contacts).

FIG. 11E shows UI 1109 including the chart at a fourth magnification. FIG. 11E also shows contacts 1130 and 1140 detected at positions 1130-a and 1140-a respectively. FIG. 11F shows contacts 1130 and 1140 detected at positions 1130-b and 1140-b respectively and shows UI 1111 including the chart at a fifth magnification (e.g., zoomed in from the fourth magnification).

FIG. 11G shows UI 1113 including the chart at a sixth magnification. FIG. 11G also shows contacts 1150 and 1160 detected at positions 1150-a and 1160-a respectively. FIG. 11H shows contacts 1150 and 1160 detected at positions 1150-b and 1160-b respectively and shows UI 1115 including the chart at a seventh magnification (e.g., zoomed in from the sixth magnification).

FIG. 11I shows UI 1117 including the chart at an eighth magnification. FIG. 11I also shows contacts 1170 and 1180 detected at positions 1170-a and 1180-a respectively. FIG. 11J shows contacts 1170 and 1180 detected at positions 1170-b and 1180-b respectively and shows UI 1119 including the chart at a ninth magnification (e.g., zoomed in from the eighth magnification).

FIGS. 12A-12D illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments. FIG. 12A shows UI 1201 including a chart at an initial magnification. FIG. 12A also shows contacts 1210 and 1220 detected at positions 1210-a and 1220-a respectively. FIG. 12B shows contacts 1210 and 1220 detected at positions 1210-b and 1220-b respectively and shows UI 1203 including the chart at a second magnification (e.g., zoomed in from the initial magnification). The relative positions of contacts 1210 and 1220 in FIG. 12B are further apart than the positions of contacts 1210 and 1220 in FIG. 12A and represent a de-pinch gesture on the touch screen. FIG. 12C shows contacts 1210 and 1220 detected at positions 1210-c and 1220-c respectively and shows UI 1205 including the chart at a third magnification (e.g., zoomed out from the second magnification). The relative positions of contacts 1210 and 1220 in FIG. 12C are closer together than the positions of contacts 1210 and 1220 in FIG. 12B and represent a pinch gesture on the touch screen. FIG. 12D shows contacts 1210 and 1220 detected at positions 1210-d and 1220-d respectively and shows UI 1207 including the chart at a fourth magnification (e.g., zoomed out from the third magnification). The relative positions of contacts 1210 and 1220 in FIG. 12D are closer together than the positions of contacts 1210 and 1220 in FIG. 12A and represent a pinch gesture on the touch screen.

FIGS. 13A-13D illustrate user interfaces for selecting chart areas, in accordance with some embodiments. FIG. 13A shows UI 1301 including a chart with selected portion 1302 and information regarding selected portion 1302. For example, FIG. 13A show information regarding the number of records in selected portion 1302. FIG. 13A also shows contact 1310 detected at position 1310-a corresponding to selected portion 1302. FIG. 13B shows UI 1303 and contact 1310 at position 1310-b and the chart with selected portion 1304 corresponding to the movement of contact 1310. FIG. 13B also shows the chart including information regarding selected portion 1304 (e.g., information showing a difference between selected portion 1302 and selected portion 1304). FIG. 13C shows UI 1305 and contact 1310 at position 1310-c and the chart with selected portion 1306 corresponding to the continued movement of contact 1310. FIG. 13C also shows the chart including information regarding selected portion 1306. FIG. 13D shows UI 1307 and contact 1310 at position 1310-d and the chart with selected portion 1308 corresponding to the continued movement of contact 1310. FIG. 13D also shows the chart including information regarding selected portion 1308.

FIGS. 14A-14D illustrate user interfaces for exporting data visualizations, in accordance with some embodiments. FIG. 14A shows UI 1401 including a chart with selected portion 1308. FIG. 14B shows UI 1403 including the chart with selected portion 1308 and selection menu 1402. FIG. 14B also shows contact 1410 detected at a position corresponding to an icon for selection menu 1402. In some embodiments, selection menu 1402 is shown in response to contact 1410 being detected over the icon for selection menu 1402. FIG. 14C shows UI 1405 including the chart with selected portion 1308 and selection menu 1402. FIG. 14C also shows contact 1420 detected at a position corresponding to a menu option (Email Image) in selection menu 1402. FIG. 14D shows UI 1407 with an email that includes information from the chart. In some embodiments, UI 1407 in FIG. 14D is shown in response to detecting contact 1420 at a position corresponding to the Email Image menu option in selection menu 1402.

FIGS. 15A-15C illustrate user interfaces for adjusting a chart view, in accordance with some embodiments. FIG. 15A shows UI 1501 including a chart. FIG. 15A also shows contact 1510 detected at position 1510-a on UI 1501. FIG. 15B shows UI 1503 and contact 1510 at position 1510-b. FIG. 15B also shows movement of the chart in concert with movement of contact 1510. For example, FIG. 15B shows both contact 1510 and the chart moving to the right from their respective positions in FIG. 15A. FIG. 15C shows UI 1505 and contact 1510 at position 1510-c. FIG. 15C also shows movement of the chart in concert with movement of contact 1510. For example, FIG. 15C shows both contact 1510 and the chart moving to the left from their respective positions in FIG. 15B.

FIGS. 16A-16D illustrate user interfaces for changing chart categories, in accordance with some embodiments. FIG. 16A shows UI 1601 including a chart with chart label 1602-1 (Average). FIG. 16A also shows contact 1610 detected at a position corresponding to chart label 1602-1. FIG. 16B shows UI 1603 including a chart with chart label 1602-2 (Percentile Bands). In some embodiments, the chart shown in FIG. 16B replaces the chart shown in FIG. 16A in response to the detection of contact 1610 at a position on the chart label.

FIG. 16C shows UI 1605 including a chart with chart label 1602-2 (Percentile Bands). FIG. 16C also shows contact 1620 detected at a position corresponding to chart label 1602-2. FIG. 16D shows UI 1607 including a chart with chart label 1602-3 (Summary). In some embodiments, the chart shown in FIG. 16D replaces the chart shown in FIG. 16C in response to the detection of contact 1620 at a position on the chart label.

FIGS. 17A-17B illustrate user interfaces for selecting chart areas, in accordance with some embodiments. FIG. 17A shows UI 1701 including a chart. FIG. 17A also shows contact 1710 detected at a position corresponding to a portion of the chart. FIG. 17B shows UI 1703 including a chart with selected portion 1702 and information regarding selected portion 1702. For example, FIG. 17B shows information regarding the number of records in selected portion 1702. FIG. 17B also shows contact 1720 detected at a position corresponding to selected portion 1702. In some embodiments, selected portion 1702 is selected in response to detecting contact 1720. In some embodiments, contact 1710 detected in FIG. 17A represents a first type of touch input (e.g., a swipe gesture) and contact 1720 detected in FIG. 17B represents a second type of touch input (e.g., a tap gesture).

FIGS. 18A-18E illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments. FIG. 18A shows UI 1801 including a chart with selected portion 1802 at an initial magnification. FIG. 18A also shows contacts 1810 and 1820 detected at positions 1810-a and 1820-a respectively. FIG. 18B shows contacts 1810 and 1820 detected at positions 1810-b and 1820-b respectively and shows UI 1803 including the chart at a second magnification (e.g., zoomed in from the initial magnification). The relative positions of contacts 1810 and 1820 in FIG. 18B are further apart than the positions of contacts 1810 and 1820 in FIG. 18A and represent a de-pinch gesture on the touch screen. FIG. 18C shows contacts 1810 and 1820 detected at positions 1810-c and 1820-c respectively and shows UI 1805 including the chart at a third magnification (e.g., zoomed in from the second magnification).

FIG. 18D shows UI 1807 including the chart at a fourth magnification. FIG. 18D also shows contacts 1830 and 1840 detected at positions 1830-a and 1840-a respectively. FIG. 18E shows contacts 1830 and 1840 detected at positions 1830-b and 1840-b respectively and shows UI 1809 including the chart at a fifth magnification (e.g., zoomed in from the fourth magnification).

FIGS. 19A-19D illustrate user interfaces for adjusting chart magnification, in accordance with some embodiments. FIG. 19A shows UI 1901 including a chart at an initial magnification. FIG. 19A also shows the chart including data marks 1902 (e.g., data marks 1902-1 through 1902-5). FIG. 19B shows UI 1903 including the chart at a second magnification (e.g., zoomed in from the initial magnification). FIG. 19B also shows the chart including data marks 1902 (e.g., a subset of data marks 1902 shown in FIG. 19A) and data marks 1904. FIG. 19C shows UI 1905 including the chart at a third magnification (e.g., zoomed in from the second magnification). FIG. 19C also shows the chart including data marks 1902 and data marks 1904. In some embodiments, data marks 1904 are initially placed on the line connecting data marks 1902 as shown in FIG. 19B and are animatedly moved (e.g., using continuous motion rather than a jump) to their respective ordinates as shown in FIG. 19C. FIG. 19D shows UI 1907 including the chart with data marks 1902 and data marks 1904 at a fourth magnification (e.g., zoomed in from the third magnification).

FIGS. 19E-19L illustrate user interfaces for displaying information about a data mark, in accordance with some embodiments. FIG. 19E shows UI 1909 including a chart at an initial magnification. FIG. 19E also shows the chart including data marks 1908 (e.g., including data marks 1908-1 and 1908-2). FIG. 19E also shows contacts 1930 and 1940 detected at positions 1930-a and 1940-a respectively. FIGS. 19F-19I show an animated transition from data mark 1908-1 to record 1914-1 in concert with movement of contacts 1930 and 1940 (e.g., the movement of contacts 1930 and 1940 represent a de-pinch gesture). Specifically, FIG. 19F shows UI 1911 including contacts 1930 and 1940 detected at positions 1930-b and 1940-b respectively and an animated transition from data mark 1908-1 to record 1914-1 in concert with movement of contacts 1930 and 1940. FIG. 19G shows UI 1913 including contacts 1930 and 1940 detected at positions 1930-c and 1940-c respectively and a continued animated transition (e.g., using continuous movement) from data mark 1908-1 to record 1914-1 in concert with movement of contacts 1930 and 1940. FIG. 19H shows UI 1915 including contacts 1930 and 1940 detected at positions 1930-d and 1940-d respectively and a continued animated transition from data mark 1908-1 to record 1914-1 in concert with movement of contacts 1930 and 1940. FIG. 19I shows UI 1917 including record 1914-1. In some embodiments, UI 1917 shown in FIG. 19I is displayed in response to ceasing to detect contacts 1930 and 1940 after completion of a de-pinch gesture (e.g., detecting lift of the contacts).

FIG. 19J shows UI 1919 including a chart at an initial magnification. FIG. 19J also shows the chart including data marks 1908 (e.g., including data marks 1908-1 and 1908-2). FIGS. 19K and 19L show an animated transition from data mark 1908-2 to record 1914-2. In some embodiments, the animated transition from data mark 1908-2 to record 1914-2 is in concert with a touch input (e.g., a de-pinch gesture).

Attention is now directed towards methods that are, optionally, implemented on portable multifunction device 100 or device 200.

FIGS. 20A-20B provide a flow diagram illustrating method 2000 of data visualization, in accordance with some embodiments. Method 2000 is performed at an electronic device (e.g., portable multifunction device 100, FIG. 1, or device 200, FIG. 2) with a display and a touch-sensitive surface. In some embodiments, the display is a touch screen display and the touch-sensitive surface is on the display. In some embodiments, the display is separate from the touch-sensitive surface. In some embodiments, method 2000 is governed by instructions that are stored in a non-transitory computer readable storage medium and that are executed by one or more processors of a device, such as the one or more processors 302 of portable multifunction device 100 and/or the one or more processors 352 of multifunction device 200, as shown in FIGS. 3A-3B. Some operations in method 2000 are, optionally, combined and/or the order of some operations is, optionally, changed.

As described below, method 2000 provides an intuitive way to display information about a data mark. This method is particularly useful when the user is interacting with a portable device and/or a compact device with a smaller screen. The method reduces the cognitive burden on the user when accessing information about a data mark, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, enabling a user to access data mark information faster and more efficiently conserves power and increases the time between battery charges.

The device displays (2002) at least a first portion of a chart on the display at a first magnification, the first portion of the chart containing a plurality of data marks (e.g., circles, squares, triangles, bars, or other representations of data points). For example, FIG. 19D shows UI 1907 including a chart with data marks 1902, 1904, and 1906.

The device detects (2004) a first touch input (e.g., a de-pinch gesture) at a location on the touch-sensitive surface that corresponds to a location on the display of the first portion of the chart. For example, FIG. 19D shows the device detecting contact 1920 and contact 1922.

In response to detecting the first touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the first portion of the chart, the device zooms (2006) in to display a second portion of the chart at a second magnification, the second portion of the chart including a first data mark in the plurality of data marks. For example, FIG. 19E shows the a zoomed in view of the chart shown in FIG. 19D in response to the device detecting contacts 1920 and 1922 and both FIG. 19D and FIG. 19E show data mark 1906-1.

While displaying the second portion of the chart at the second magnification, the device detects (2008) a second touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the second portion of the chart. For example, FIG. 19E shows the device detecting contact 1930 at position 1930-a and contact 1940 at position 1940-a.

In some embodiments, the second touch input is (2010) a same type of touch input as the first touch input (e.g., both the first touch input and the second touch input are de-pinch gestures). For example, contacts 1210 and 1220 shown in FIG. 19D and contacts 1930 and 1940 shown in FIGS. 19E-19H each represent a de-pinch gesture.

In response to detecting the second touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart (2012), the device, in accordance with a determination that one or more predefined data-mark-information-display criteria are not met, zooms (2014) in to display a third portion of the chart at a third magnification, the third portion of the chart including the first data mark in the plurality of data marks.

In response to detecting the second touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart (2012), the device, in accordance with a determination that the one or more predefined data-mark-information-display criteria are met, displays (2016) information about the first data mark. In some embodiments, while displaying information about the first data mark, the device detects a third touch input on the touch-sensitive surface; and in response to detecting the third touch input, ceases to display the information about the first data mark and display a fourth portion of the chart. In some embodiments, the fourth portion of the chart is the second portion of the chart. For example, FIGS. 19E-19I show movement of contacts 1930 and 1940 representing a de-pinch gesture. FIGS. 19E-19I also show an animated transition from UI 1909 including data mark 1908-1 to UI 1917 including record 1914-1 (e.g., information about data mark 1908-1).

In some embodiments, the information about the first data mark comprises (2018) a data record that corresponds to the first data mark. For example, FIGS. 19E-19I also show an animated transition from UI 1909 including data mark 1908-1 to UI 1917 including record 1914-1.

In some embodiments, the data-mark-information-display criteria include (2020) the second magnification being a predefined magnification. For example, if the first touch input zooms in the chart to a predefined maximum magnification, then the second touch input causes the display of the information about the first data mark, instead of (or in addition to) causing continued zooming in of the chart.

In some embodiments, the data-mark-information-display criteria include (2022) the first data mark in the plurality of data marks being the only data mark displayed at the second magnification after the first touch input. For example, if the first touch input zooms in the chart so that only the first data mark is displayed, then the second touch input causes the display of the information about the first data mark, instead of (or in addition to) causing continued zooming in of the chart.

In some embodiments, the data-mark-information-display criteria include (2024) the first data mark reaching a predefined magnification during the second touch input. In some embodiments, if the first data mark reaches a predefined magnification during the second touch input (e.g., during a de-pinch gesture), then the device zooms in during the second touch input prior to reaching the predefined magnification, and the device displays the information about the first data mark after reaching the predefined magnification (with or without continuing to zoom in the chart during the remainder of the second touch input).

In some embodiments, the data-mark-information-display criteria include (2026) the device zooming in to display only the first data mark in the plurality of data marks during the second touch input. In some embodiments, if during the second touch input (e.g., a de-pinch gesture), the device zooms in such that the first data mark is the only data mark that is displayed, the device displays the information about the first data mark after the first data mark is the only data mark that is displayed (with or without continuing to zoom in the chart during the remainder of the second touch input).

In some embodiments, in accordance with the determination that one or more predefined data-mark-information-display criteria are met, the device ceases (2028) to display the first data mark. In some embodiments, the display of the first data mark is replaced by the display of a data record that corresponds to the first data mark when the one or more predefined data-mark-information-display criteria are met (e.g., via an animated transition). For example, FIGS. 19E-19I also show an animated transition where the display of record 1914-1 replaces the display of data mark 1908-1.

FIGS. 21A-21F illustrate how some embodiments allow scrolling through filter selections, with the data visualization updated immediately as the filter changes. These figures provide bar charts showing total sales for a three month period in 2014, and the data is filtered by region. In this example, the four regions are Central, East, South, and West.

Initially, the user has filtered the data to display sales data for just the Central region, as shown in FIG. 21A. Filter indicia 2108 include a scrollable region indicator that indicates Central selection 2112-C. Corresponding to this filter selection, user interface 2101 displays visual graphic 2110-C, which shows data for the Central region. In FIG. 21B, the user wants to compare the Central region to the other regions, and the device detects contact 2114 at position 2114-a corresponding to Central selection 2112-C. At this time user interface 2101 still displays the visual graphic 2110-C for the Central region.

In FIG. 21C, the user has started scrolling upwards (e.g., using a swipe gesture), so contact 2114 is moving upwards to position 2114-b. At this time, the scrollable region indicator is transitioning from “Central” to “East,” so selection 2112-C/E is in an interim state. Visual graphic 2110-C is still the graphic for the Central region. When the scrollable region indicator displays East selection 2112-E, as illustrated in FIG. 21D, visual graphic 2110-E, including data for the East region, is displayed. At this time, contact 2114 is still moving upwards to position 2114-c. As illustrated in FIG. 21E, contact 2114 has moved upward to position 2114-d and the indicator shows “South” region selection 2112-S. When the scrollable region indicator shows the South region, the user interface displays visual graphic 2110-S including data for the South region.

As illustrated in FIG. 21E, contact 2114 is still moving upwards to position 2114-e, so the scrollable region indicator comes to West region selection 2112-W, as illustrated in FIG. 21F. When this occurs, the user interface displays the data for the West region in visual graphic 2110-W.

As illustrated by FIGS. 21A-21F, a user can quickly scroll through filter values, and the visual graphic updates according to the filter as different filter values are selected. In some embodiments, the updates to the display depend on the scroll speed. For example, if the scrolling is performed slowly, the visual graphic is updated for each filter value as illustrated in FIGS. 21A-21F. On the other hand, if the values are scrolled quickly, a user is probably not interested in the intermediate values, and thus the visual graphic is not updated until the scrolling slows down or stops.

It will be understood that, although the terms “first,” “second,” etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first contact could be termed a second contact, and, similarly, a second contact could be termed a first contact, without changing the meaning of the description, so long as all occurrences of the “first contact” are renamed consistently and all occurrences of the second contact are renamed consistently. The first contact and the second contact are both contacts, but they are not the same contact.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. As used in the description of the embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined [that a stated condition precedent is true]” or “if [a stated condition precedent is true]” or “when [a stated condition precedent is true]” may be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.

The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain principles of operation and practical applications, to thereby enable others skilled in the art. 

What is claimed is:
 1. A method, comprising: at an electronic device with a touch-sensitive surface and a display: displaying at least a first portion of a chart on the display at a first magnification, the first portion of the chart containing a first plurality of data marks, wherein a first data mark in the first plurality of data marks corresponds to a plurality of data points from a database; detecting a first touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the first portion of the chart; in response to detecting the first touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the first portion of the chart, zooming in to display a second portion of the chart at a second magnification, including replacing the first data mark with a second plurality of data marks, each corresponding to a respective data point in the plurality of data points, wherein the second plurality of data marks includes a second data mark; while displaying the second portion of the chart at the second magnification, detecting a second touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the second portion of the chart; in response to detecting the second touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart, zooming in to display a third portion of the chart at a third magnification, the third portion of the chart including the second data mark in the second plurality of data marks; while displaying the third portion of the chart at the third magnification, detecting a continuation of the second touch input; and, in response to detecting the continuation of the second touch input, and in accordance with a determination that the second data mark corresponds to a single data point, replacing the second data mark with a visual record that includes information about the single data point.
 2. The method of claim 1, wherein the second touch input is a same type of touch input as the first touch input.
 3. The method of claim 1, wherein replacing the second data mark with the visual record is further in accordance with the third magnification being a predefined magnification.
 4. The method of claim 1, wherein replacing the second data mark with the visual record is further in accordance with the second data mark being the only data mark displayed at the third magnification during the second touch input.
 5. The method of claim 1, wherein replacing the second data mark with the visual record includes displaying an animated transition from the second data mark to the visual record.
 6. The method of claim 1, wherein the first touch input and the second touch input are respective portions of a continuous touch input.
 7. An electronic device, comprising: a display; a touch-sensitive surface; one or more processors; memory; and one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for: displaying at least a first portion of a chart on the display at a first magnification, the first portion of the chart containing a first plurality of data marks, wherein a first data mark in the first plurality of data marks corresponds to a plurality of data points from a database; detecting a first touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the first portion of the chart; in response to detecting the first touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the first portion of the chart, zooming in to display a second portion of the chart at a second magnification, including replacing the first data mark with a second plurality of data marks, each corresponding to a respective data point in the plurality of data points, wherein the second plurality of data marks includes a second data mark; while displaying the second portion of the chart at the second magnification, detecting a second touch input at a location on the touch-sensitive surface that corresponds to a location on the display of the second portion of the chart; in response to detecting the second touch input at the location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart, zooming in to display a third portion of the chart at a third magnification, the third portion of the chart including the second data mark in the second plurality of data marks; while displaying the third portion of the chart at the third magnification, detecting a continuation of the second touch input; and, in response to detecting the third touch input at the continuation of the second touch input, and in accordance with a determination that the second data mark corresponds to a single data point, replacing the second data mark with a visual record that includes information about the single data point.
 8. The device of claim 7, wherein the second touch input is a same type of touch input as the first touch input.
 9. The device of claim 7, wherein replacing the second data mark with the visual record is further in accordance with the third magnification being a predefined magnification.
 10. The device of claim 7, wherein replacing the second data mark with the visual record is further in accordance with the second data mark being the only data mark displayed at the third magnification during the second touch input.
 11. The device of claim 7, wherein replacing the second data mark with the visual record includes displaying an animated transition from the second data mark to the visual record.
 12. The device of claim 7, wherein the first touch input and the second touch input are respective portions of a continuous touch input.
 13. A non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by an electronic device with a display, and a touch-sensitive surface, cause the device to: display at least a first portion of a chart on the display at a first magnification, the first portion of the chart containing a first plurality of data marks, wherein a first data mark in the first plurality of data marks corresponds to a plurality of data points from a database; in response to detecting a first touch input at a location on the touch-sensitive surface that corresponds to the location on the display of the first portion of the chart, zoom in to display a second portion of the chart at a second magnification, including replacing the first data mark with a second plurality of data marks, each corresponding to a respective data point in the plurality of data points, wherein the second plurality of data marks includes a second data mark; and, in response to detecting, while displaying the second portion of the chart at the second magnification, a second touch input at a location on the touch-sensitive surface that corresponds to the location on the display of the second portion of the chart, zoom in to display a third portion of the chart at a third magnification, the third portion of the chart including the second data mark in the second plurality of data marks; and, in response to detecting, while displaying the third portion of the chart at the third magnification, a continuation of the second touch input, and in accordance with a determination that the second data mark corresponds to a single data point, replace the second data mark with a visual record that includes information about the single data point.
 14. The non-transitory computer readable storage medium of claim 13, wherein replacing the second data mark with the visual record includes displaying an animated transition from the second data mark to the visual record.
 15. The non-transitory computer readable storage medium of claim 13, wherein the first touch input and the second touch input are respective portions of a continuous touch input. 